What's New in Release 14.4.2 & 14.5.0
May 7, 2025
Inbox renamed to My Claims
We found that the term "Inbox" did not clearly convey to users that this space contained their assigned work. To better reflect its purpose, we have renamed it "My Claims."
Name change on the navigation bar:
Name change on the My Claims page:
Dashboard - "My claims viewed today" changed to "Claims viewed today":
Using Advanced Search to send claims to collections
You can now send claims to collections directly from the Advanced Search results window.
-
Click
from the navigation bar.
-
Enter your search criteria and then click Search.
-
On the Search Results window, use the far left checkbox to select which claims you wish to send to collections. If needed, use the top checkbox to select all the claims at once.
-
Click the Move to collection agency button.
-
On the Move to Collection Agency window, select the agency or create a new one.
-
Click Confirm.
-
If you select multiple claims and one or more either do not have the patient as the payer or have been closed, a message will appear informing you that those claims will not be moved to the collection agency. The number of claims that will be moved will be displayed at the bottom of the message.
-
Click Continue.
-
A confirmation message displays. If you are ready to move the selected claims to collections, click Yes.
Ignore a payment from the Resolve window
You can now use the new "Ignore payment – do not allocate to claim" option in the Resolve window to ignore the "Review Required" line item for a payer not found on an account.
After clicking this option the line item will display in the Ignored section in Payment Posting. If the user restores the payment to a "Resolve" status, the item will not be available for posting until the issue is corrected.
Additional HCPCS J3424
HCPCS "J3424 - Injection, hydroxocobalamin, intravenous, 25 mg" is now available for use in ZOLL Billing.
Adjust off balance and close change
Prior to release 14.5.0, when using the "Adjust off balance and close" option during Review Needed, the revenue adjustment was posted with a "Medicaid not covered" description under the patient payer entry on the claim. Now, if Medicaid is the payer and this option is selected, the revenue adjustment is posted to Medicaid instead of the patient. This change applies only when Medicaid is the payer and will display as a Medicaid revenue adjustment in the correct accounting period.
The following issues were fixed in release 14.4.2 & 14.5.0:
-
Hot fix released 4/29: Older invoices that do not have an associated invoice number will now display an N/A in the "Invoice #" column on the Facility page > Facility details tab.
-
Hot fix released 4/29: A user posted a obsolete revenue adjustment to the patient payer to resolve the balance. They found that after posting adjustment to the other payer, it impacted the “Facility amount due” value on the facility and showed an inaccurate value for the claim in the Outstanding claims tab.
-
Hot fix released 4/25: Claims were not showing a unique invoice number when a user generated an invoice using the "Separate invoices, one per claim" option.
-
Hot fix released 4/25: The facility balance value was not showing correctly on each tab on the Facilities page.
-
The option to "Move to patient and suspend" was being wrongfully presented when a payment was being applied to a primary payer and there was a secondary payer on the claim. This option will now only be available if the next payer is the patient.
-
When two separate policies with the same benefit plan existed under a single payer entry with different member IDs, the user was unable to create a transaction and therefore unable to post a payment.
-
If the current payer on a claim has a policy type of Medicaid or Managed Medicaid Care, the "Ignore payment – do not allocate to claim" option was not working correctly. A red error message displayed and the user was prevented from proceeding.
-
Pre-billers were reporting issues where a signature was not saved on an incomplete claim. After the claim was complete, the Signature section was showing multiple signatures resulting in manual editing to correct.
-
A user posting an adjustment greater than five million dollars caused the claim to be stuck in an error state. Now, we restrict the maximum amount of a single writeoff/adjustment to $9,999,999.99.
-
When users edited the price per unit with a custom amount and then completed the claim they found that system default charge was being applied to the claim instead of the custom amount.
-
A user used the "Add a line item" functionality to add multiple line items for a patient payment. They then reversed the payment on the second credit but found that it was reversing on the first credit instead.
-
The system was configured so that claims would be created from NEMSIS documentation and only created from a Dispatch record if the NEMSIS documentation did not arrive within 72 hours. The user found that the claim was being created from the Dispatch record before the 72-hour waiting period expired.
-
The system was allowing users to edit the COB after the claim was moved to collections.